

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<html>
<head>
<script type="text/javascript" src="helpman_topicinit.js"></script>

<title>Business Analysts [Enterprise Architect User Guide]</title>

<meta name="keywords" content="Enterprise Architect, Sparx Systems, UML, Project Role,Project Role Business Analyst,Business Analyst,Business Analyst Project Role,Business Analyst And Enterprise Architect,Enterprise Architect,Enterprise Architect For Business Analysts">
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
<meta http-equiv="Content-Style-Type" content="text/css" />

<link type="text/css" href="default.css" rel="stylesheet" />
<style type="text/css">
  A, A:Visited
  {
    color: #00F;
  }

  A:Active, A:Hover
  {
    color: #F00;
  }

  OL
  {
    margin: 5px 0 5px 48px;
  }

  UL
  {
    margin-bottom: 3px;
    margin-top: 0;
  }

  #nsr
  {
    background-color: #D4DFFF;
  }

  #nsr A
  {
    text-decoration: none;
  }

  #mainbody
  {
    padding: 8px;
  }

  .p_BodyText
  {
    padding: 5px 0;
  }
</style>



<style type="text/css" media="screen">
  BODY
  {
    background-color: #FFFFFF;
  }

  #nsr
  {
    padding: 6px 6px 0 6px;
    border-bottom: none;
    vertical-align: top;
    z-index: 2;
    visibility: visible;
    left: 0;
    top: 0;
    position: absolute;
  }

  #mainbody
  {
    left: 0;
    top: 0;
    margin: 0;
    position: absolute;
    padding: 10px;
    overflow: auto;
    height: 100%;
    z-index: 1;
    background-repeat: no-repeat;
    background-position: bottom right;
    background-attachment: fixed;
  }
</style>

<style type="text/css" media="print">
  #nsr
  {
    visibility: none;
  }

  #mainbody
  {
    overflow: visible;
  }
</style>
<script type="text/javascript" language="JavaScript" src="nonscroll.js"></script>

</head>
<body scroll="no">

<div id="page">



        <div id="content">
          <div id="content-inner">
          



  
          <div id="nsr">
            <table border="0" cellspacing="0" cellpadding="4" width="100%">
              <tr valign="top">
                <td align="left">
  


                  <p class="p_Heading1"><span class="f_Heading1">Business Analysts</span></p>



  
                </td>
                <td align="right">
                  <a href="introduction.htm" onmouseover="document.images.main.src='button_main_h.gif'" onmouseout="document.images.main.src='button_main.gif'">
                    <img name="main" src="button_main.gif" border=0 alt="Return to Introduction">
                  </a>&nbsp;
    
                  <a href="professionalroles.htm" onmouseover="document.images.prev.src='button_prev_h.gif'" onmouseout="document.images.prev.src='button_prev.gif'">
                    <img name=prev src="button_prev.gif" border=0 alt="Previous page" />
                  </a>&nbsp;
    
    
    
                  <a href="softwarearchitects.htm" onmouseover="document.images.next.src='button_next_h.gif'" onmouseout="document.images.next.src='button_next.gif'">
                    <img name=next src="button_next.gif" border=0 alt="Next page" />
                  </a>
    
    
                </td>
              </tr>
            </table>
          </div>
          <div id="mainbody">
  


                <p class="p_BodyText"><span class="f_BodyText">A Business Analyst can use Enterprise Architect to create high-level <a href="businessmodelling.htm">models of business processes</a>. These include business requirements, activities, work flow, and the display of system behavior. Using Enterprise Architect, a Business Analyst can describe the procedures that govern what a particular business does. Such a model is intended to deliver a high-level overview of a proposed system.</span></p>
<p class="p_TextIndentedL2"><img src="example%20of%20an%20analysis%20diagram.png" width="773" height="537" border="0" alt="Example of an Analysis Diagram"></p>
<p class="p_SubHeadingL1"><span class="f_SubHeadingL1">Model High Level Business Processes</span></p>
<p class="p_BodyText"><span class="f_BodyText">With Enterprise Architect the Business Analyst can model high level processes of the business with <a href="analysisdiagram.htm">Analysis diagrams</a>. Analysis diagrams are a subset of UML 2.1.1 Activity diagrams and are less formal than other diagram types, but they provide a useful means for expressing essential business characteristics and requirements.</span></p>
<p class="p_SubHeadingL1"><span class="f_SubHeadingL1">Model Requirements</span></p>
<p class="p_BodyText"><span class="f_BodyText"><a href="requirementsmanagement2.htm">Gathering requirements</a> is typically the first step in developing a solution, be it for developing a software application or for detailing a business process. It</span><span class="f_BodyText"> is an important step in the implementation of a project. Enterprise Architect enables you to define the Requirement elements, connect Requirements to the model elements for implementation, connect Requirements together into a hierarchy, report on Requirements, and move Requirements out of model element responsibilities.</span></p>
<p class="p_SubHeadingL1"><span class="f_SubHeadingL1">Model Business Activities</span></p>
<p class="p_BodyText"><span class="f_BodyText">The Business Analyst can use <a href="activitydiagram.htm">Activity diagrams</a> to model the behavior of a system and the way in which these behaviors are related to the overall flow of the system. Activity diagrams do not model the exact internal behavior of the system but show instead the general processes and pathways at a high level.</span></p>
<p class="p_SubHeadingL1"><span class="f_SubHeadingL1">Model Work Flow</span></p>
<p class="p_BodyText"><span class="f_BodyText">To visualize the cooperation between elements involved in the work flow, the Business Analyst can use an <a href="interactionoverviewdiagram.htm">Interaction Overview diagram</a>, which provides an overview of sub activities that are involved in a system.</span></p>
<p class="p_SubHeadingL1"><span class="f_SubHeadingL1">Display System Behavior</span></p>
<p class="p_BodyText"><span class="f_BodyText">In displaying the behavior of a system as a </span><span class="f_Bulletlist1"><a href="usecasediagram.htm">Use Case diagram</a></span><span class="f_BodyText">, Enterprise Architect gives the Business Analyst an easily understood tool for mapping the functional requirements and behavior of a system.</span></p>




            </div>
          </div>
        </div>



</div>


</body>
</html>
